chore(scripts): wire provenance check into pre-pr#91
Open
satwareAG-ironMike wants to merge 1 commit into
Open
Conversation
Add [5/5] step to scripts/bash/pre-pr.sh that calls $SATWARE_HARNESS/scripts/check-speckit-cli.sh before pushing. Fatal when the system `specify` resolves to anything other than the satwareAG fork at a pushed satware-v* release tag. Skipped gracefully when SATWARE_HARNESS is unset or the script is not executable, so contributors without the satware harness can still run pre-pr. Pairs with satware/harness rules/tool.provenance.md. Assisted-by: opencode z-ai/glm-5.2 (autonomous)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add
[5/5]step toscripts/bash/pre-pr.shthat calls$SATWARE_HARNESS/scripts/check-speckit-cli.shbefore pushing. Fatal when the systemspecifyresolves to anything other than the satwareAG fork at a pushedsatware-v*release tag.Background
A real incident triggered this: an ambient
uv tool installfrom upstreamgithub/spec-kitwas silently shadowing the fork's editable venv (Common Pitfall #6 in this repo's AGENTS.md), running stale0.8.15.dev0instead of the satwareAGv0.13.0release. The satwareAG fork uses asatware-vX.Y.Z+Ntag scheme; a local-onlyv0.13.0tag from an upstream leftover was never the satwareAG release.Changes
scripts/bash/pre-pr.sh(+20/-4): new[5/5]step calls$SATWARE_HARNESS/scripts/check-speckit-cli.sh. Fatal on exit 2 (foreign / missing / untagged). Skipped gracefully whenSATWARE_HARNESSis unset or the script is not executable, so contributors without the satware harness can still run pre-pr.[1/4]...[4/4]->[1/5]...[4/5].Pairs With
satware/harness PR #64:
feat(security): add tool provenance rule + check script- adds thecheck-speckit-cli.shscript andrules/tool.provenance.mdpolicy that this change invokes.Test Plan
bash scripts/daily-routine.sh pre-prend-to-end:=== pre-pr: all checks passed ===OK: specify 0.13.0 (uv-tool, satware-v0.13.0+1 @ 5ddf6a312a1b)SATWARE_HARNESSunset: printsskipped (SATWARE_HARNESS not set or check-speckit-cli.sh not found)🤖 Assisted-by: opencode z-ai/glm-5.2 (autonomous)